Yeti

Guerilla Render can render the Yeti's procedural geometries.

Installation

Linux

Guerilla uses the pgYetiPrmanRender DSO and the pgYetiCacheInfo application. The Yeti bin directory should be added to the LD_LIBRARY_PATH and PATH variable before running "guerilla" or "render".

Because both Guerilla and Yeti depend on tbb, it is possible that redefining LD_LIBRARY_PATH causes Guerilla to link against Yeti's libtbb.so. Depending on Yeti's version, this can prevent Guerilla from running, in which case you have to prepend /usr/local/guerilla/lib (adapt this to your actual installation) before Yeti's path in LD_LIBRARY_PATH.

Windows

Guerilla uses the pgYetiPrmanRender DLL and the pgYetiCacheInfo application. The Yeti bin directory should be added to the PATH variable before running "guerilla" or "render". It should be the case on a standard Yeti installation.

Yeti Shader Attributes

The curve shader is fully functional with the Yeti curves. The surface texture coordinates "st", the curve ids and the surface normal are handled like any other curves in Guerilla.

Pre-baking Yeti bounding boxes

Guerilla uses Yeti's pgYetiCacheInfo to extract the bounding box information for the fur cache, which can seriously slow down the workflow in Guerilla.

You can cache this evaluation in a .bbox file next to the .fur file. Guerilla will read this file instead of running pgYetiCacheInfo. To bake this bounding box, proceed as follow for each .fur file (in a bash/batch command line):

pgYetiCacheInfo --bounding_box --file my_file.0023.fur > my_file.0023.bbox

where my_file.0023 should obviously be replaced with the proper file.

Overriding Yeti Attributes

Use the YetiAttributes rendergraph node to override a Yeti node. All parameters, such as Density, Length, Width, Fur file and Boundig box extension can be overriden with this node.

Only the Yeti node can be overriden. Yeti exported as a Rib box cannot be overriden.